feat: Add support authorization key provider #531
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-cloud Signed-off-by: Vladislav Polyakov <[email protected]>
|
Hi @chezzyderp, Thank you for the effort on this PR. The main reason we can’t merge it right now is that the solution isn’t A cleaner approach would be to isolate this functionality into its own npm package. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that in the new version of the package there is no alternative for getSACredentialsFromJson and IamService. Therefore, I want to suggest creating a new Provider that will receive the SA Authorization Key and generate an IAM to access the service. I'm really looking forward to your feedback